About licensing

Meridian Explorer and Accruent Publisher usage is controlled by licenses to authorize their various features. These licenses are managed by the Meridian Enterprise license server to which Meridian Enterprise Server is configured as described in Managing licenses. The licenses and their usage can also be viewed in Meridian Enterprise Server Administration Console.

Note:

Some of the client licenses described below are also available as named licenses, in which case the part numbers begin with MN-.

The Meridian Explorer licenses are:

  • BC Explorer Server License (part number includes M--EXS). One is required for each Meridian Enterprise server that is synchronized with a Meridian Explorer repository (excluding the Meridian Enterprise Data Library).

  • BC Explorer Base, Standard, and Plus client licenses (part numbers include M--EXB, M--EXC, M--EXP). Each license type enables specific client functionality:

    • Explorer Base – all basic functionality such as:
      • Documents view
      • Collections view
      • General, Properties, Revisions, References, and Project Copies property pages
    • Explorer Standard – all functionality of Explorer Base plus:
      • Projects view
      • Feedback property page (requires AutoVue for redlining)
      • Packages property page and package import/export
      • Dashboard page
    • Explorer Plus – all functionality of Explorer Standard plus:
      • Tags view
      • Tag search
      • Related Tags property page

    One license is required for every concurrent Meridian Explorer user and the license remains claimed  for the duration of the browser session (except by mobile users, see below).

    Note:
    • Meridian Explorer client licenses will be substituted automatically by a PowerUser client (M--PUR) license (if available) when a user opens the PowerUser client while one of the licenses are claimed. The licenses are not substituted in reverse. That is, when a user has claimed a PowerUser license and opens the Meridian Explorer client, no additional Meridian Explorer license is claimed. The PowerUser license entitles the user to work in Meridian Explorer and the PowerUser license remains claimed. License substitution does not occur between concurrent and named licenses.
    • PowerUser client (M--PUR) licenses will be claimed by Meridian Explorer users if no Meridian Explorer user licenses are available.
    • Each user of the mobile version of the Meridian Explorer website permanently claims a BC Explorer Base, Standard, or Plus Client License (part numbers include M--EXB, M--EXC, M--EXP), whichever is available.
    • Client licenses expire after 30 minutes of inactivity. This is not configurable.
  • AutoVue 2D Viewer License and AutoVue 3D Viewer License (part number includes M--AV2 or M--AV3, respectively). One is required for every (concurrent or named license) user with a PC that has the viewer installed. The AutoVue 3D Viewer License is claimed when the user is viewing any document regardless of its type. How the viewer is used can be configured as described in Configuring the viewer options.

The Publisher system link licenses are:

  • BC Meridian Enterprise link (part number includes M--PUS) for publishing to or from a  Meridian Enterprise vault .

    Note:

    One Meridian Enterprise database connection license (Hypertrieve, SQL Server, or Oracle) is required for each Meridian Enterprise Server computer (cluster node) that publishes to or from a Meridian Enterprise vault.

  • Windows file system link (part number includes FS-PUS) for publishing to or from a Windows file system.
  • SharePoint system link (part number includes M--PSP) for publishing to or from a SharePoint library.

  • Kronodoc system link (part number includes K--PUS) for publishing to or from a Accruent Project Portal or Kronodoc workspace.

    All system link licenses include the use of:

    • AutoVue 2D rendering module. Rendering 3D models requires an AutoVue 3D license.
    • Meridian Enterprise vault extensions
    • Client applications to support publishing from that system

The Publisher rendering module licenses are:

  • Native Application rendering module (part number includes M--PNR) for rendering through AutoCAD, Autodesk Inventor, Microsoft Office, MicroStation, SolidWorks, or the Custom rendering module.
  • eSignature module (part number includes M--PES) for applying watermarks, electronic signatures, and signature pages to renditions.
  • PDF Merge rendering module (part number includes M--PMD) for merging renditions into a single Adobe PDF file.
Note:

When configured in a cluster, all Meridian Enterprise Server nodes (primary and secondary) require their own system link and rendering module licenses for the jobs that they process.

To obtain additional licenses, contact your Accruent Partner or Accruent. For more information about registering licenses in the Accruent License Server, see the Accruent Meridian Enterprise Administrator's Guide.